fix(KeyValueCache): allow negative TTL for file locking#62114
Merged
Conversation
file locking uses negative TTL, returning the default will break. Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
susnux
requested review from
CarlSchwan,
leftybournes,
provokateurin and
salmart-dev
and removed request for
a team
July 14, 2026 16:56
CarlSchwan
approved these changes
Jul 15, 2026
susnux
enabled auto-merge
July 15, 2026 14:47
AndyScherzinger
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
file locking uses negative TTL, returning the default will break.
Checklist
3. to review, feature component)stable32)AI (if applicable)